home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000217-20000824
/
000395_news@columbia.edu _Thu Jun 22 04:39:40 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-08-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id EAA05342
for <kermit.misc@cpunix.cc.columbia.edu>; Thu, 22 Jun 2000 04:39:39 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id EAA20192
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 22 Jun 2000 04:39:38 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id EAA09252
for kermit.misc@watsun.cc.columbia.edu; Thu, 22 Jun 2000 04:20:43 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: bernd@lipid.fki.dtu.dk (Bernd Dammann)
Subject: Re: Serial console: Ctrl-C doesn't work
Date: 22 Jun 2000 08:12:26 GMT
Organization: The Technical University of Denmark
Message-ID: <8ishpa$15v6$1@news.net.uni-c.dk>
To: kermit.misc@columbia.edu
Frank da Cruz (fdc@watsun.cc.columbia.edu) wrote:
: In article <8i7c8n$11ro$1@news.net.uni-c.dk>,
: Bernd Dammann <bernd@lipid.fki.dtu.dk> wrote:
: : I've set up a diskless and headless machine with a serial console that
: : I access from the server through a null-modem cable (using kermit as
: : terminal emulator). Everything works fine, except for one thing:
: :
: : Ctrl-C (intr) and Ctrl-Z (susp) don't work! All other Ctrl- sequences
: : like Ctrl-U (kill) and Ctrl-W (werase) do work.
: :
: : Where is the problem? The console settings (see below), or the
: : terminal emulation? I've tried several terminal emulation programs
: : (i.e. kermit, minicom, ...), but the problem is the same.
: :
: So it's evidently something with your Linux configuration, having nothing
: to do with the terminal emulator.
You are right, I found out what went wrong:
Linux has the following devices
crw------- 1 root root 5, 1 Jun 16 16:32 /dev/console
crw------- 1 root tty 4, 64 Jun 14 17:15 /dev/ttyS0
and I had set up getty on /dev/console (which worked for me before on
an older Linux system (kernel < 2.0):
con:2345:respawn:/sbin/getty console DT38400 vt100
The right thing to do is:
con:2345:respawn:/sbin/getty ttyS0 DT38400 vt100
since /dev/console is a device for its own in newer Linux systems.
That solved the problem.
Bernd
--
# Bernd Dammann <bernd@fki.dtu.dk> | "Why stop now,
# Department of Physical Chemistry | just when I am hating it?"
# The Technical University of Denmark |---------------------------------
# Building 206 | phone: (+45) 45 25 24 81
# DK-2800 Lyngby, Denmark | http://www.fki.dtu.dk/~bernd/